fix(ssr): skip esm proxy guard for namespace imports #14988
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
repro https://github.com/brillout/vite-regression-2023-nov-14
We add the ESM proxy guard unconditionally to error when you import something like:
However, we don't have to add the guard for
This PR fixes this by checking if they are imported names from the
./mod
before adding the guard. In which case, namespace imports would never have imported names.Other things I changed along the way:
namedImportSpecifiers
toimportedNames
: Matches the AST name and because the array can now include"default"
when you doimport mod from './mod'
. In reality, this is the same asimport { default as mod } from './mod'
and I noticed Node.js handles this way too.[vite]
prefix so we can easily identify if it's coming from Vite in the future.Additional context
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).